Troubleshoot Red Hat Edge Manager

When working with devices in Red Hat Edge Manager, you might see issues related to configuration, connectivity, or deployment. Troubleshooting these issues requires understanding how device configurations are applied, how to check logs, and how to verify communication between the device and service.

View a device’s effective target configuration
Copy link

The device manifest returned by the flightctl get device command still only has references to external configuration and secret objects. Only when the device agent queries the service, the service replaces the references with the actual configuration and secret data.

About this task
Copy link

While this better protects potentially sensitive data, it also makes troubleshooting faulty configurations hard. This is why a user can be authorized to query the effective configuration as rendered by the service to the agent.

Procedure
Copy link

To query the effective configuration, use the following command: 
flightctl get device/${device_name} --rendered | jq

Generate a device log bundle
Copy link

Use the integrated flightctl-must-gather script directly on the device to generate a comprehensive bundle of diagnostic logs. This log bundle, in a standard .tar format, provides the necessary data to debug the device agent and assists in efficient troubleshooting and bug reporting.

Procedure
Copy link

Run the following command on the device and include the .tar file in the bug report.
Note

This depends on an SSH connection to extract the .tar file.

 
sudo flightctl-must-gather